@akronim26 can you fix ci?

@akronim26 can you fix ci?

@KolbyML, I think the codebase should also allow using .map_err(|_| ...) in addition to .map_err(|err| ...). In cases like this, the underlying error isn’t needed or isn’t accessible at that layer. Alternatively, is there a preferred pattern for handling this kind of situation so that the code doesn’t end up forcing an unused error binding?

Actually the ci is failing due to this

@akronim26 can you fix ci?

@KolbyML, I think the codebase should also allow using .map_err(|_| ...) in addition to .map_err(|err| ...). In cases like this, the underlying error isn’t needed or isn’t accessible at that layer. Alternatively, is there a preferred pattern for handling this kind of situation so that the code doesn’t end up forcing an unused error binding?

Actually the ci is failing due to this

I disagree, I don't think we should be using InvalidByteLength for those, we should add a new error type to our this_error struct.

Those errors being hidden may not be related to InvalidByteLength

Hi @KolbyML! When you get a moment free, could you please review this?